Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.claude/rules/coding-style.md:
- Around line 31-34: Update the naming-conventions bullet for "New files" so it
reflects the actual project conventions instead of the aspirational ones: change
the custom route file example from snake_case (e.g., `user_profile.ts`) to plain
lowercase filenames (e.g., `auth.ts`, `kanban.ts`) and change the directory
convention example from kebab-case (e.g., `user-profile/`) to
underscore-prefixed directories (e.g., `_utils`, `_fixtures`, `_types`); keep
SvelteKit special file guidance as-is (`+page.svelte`, `+page.server.ts`,
`+server.ts`).

In @.claude/settings.json:
- Around line 5-10: The marketplace source under "extraKnownMarketplaces" ->
"superpowers-dev" currently points to a floating git URL; update the "source"
object (the entry with keys "source" and "url") to include a pinned Git ref by
adding a "ref" field set to the appropriate tag (e.g., "v1.0.0") so the "source"
object becomes stable and reproducible.

In @.coderabbit.yaml:
- Around line 44-47: The rules for the services path are self-contradictory:
update the instructions for the path 'src/**/services/**' to remove the circular
"No direct Prisma calls — delegate to service layer" line and replace it with a
clear rule such as "Service functions must return pure values or null; never
Response/json(). Service files may call Prisma directly — avoid database access
in controllers/handlers; keep Prisma usage encapsulated in services." Ensure the
change targets the existing instructions block for 'src/**/services/**' so
reviewers enforce services as the layer that may access Prisma while
controllers/handlers remain DB-free.
- Around line 11-22: The top-level exclusion '!prisma/migrations/**' prevents
the path_instructions for path 'prisma/**' (the migration rules) from ever
running; remove or modify that exclusion so migration files are not ignored
(e.g., delete the '!prisma/migrations/**' entry or replace it with a
non-excluding pattern) so the 'prisma/**' path_instructions (Migration files
must not be edited..., CHECK constraints documented in prisma/ERD.md) can be
enforced against prisma/migrations files.

In @.devcontainer/devcontainer.json:
- Line 28: Update the devcontainer postCreateCommand so the CodeRabbit installer
is pinned by exporting CODERABBIT_VERSION before invoking the installer; modify
the "postCreateCommand" string to set CODERABBIT_VERSION=<pinned-version> (e.g.,
v1.2.3) for the curl | sh step while preserving the existing chained commands
(npm install -g `@anthropic-ai/claude-code` and pnpm install) referenced in the
postCreateCommand entry in .devcontainer/devcontainer.json.